Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/2490/

Test Failed. https://jenkins.esgyn.com/job/Check-PR-master/2490/

I can't see where the tests failed.

New Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/2491/

Test Failed. https://jenkins.esgyn.com/job/Check-PR-master/2491/

New Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/2492/

Test Failed. https://jenkins.esgyn.com/job/Check-PR-master/2492/

https://jenkins.esgyn.com/job/static-checks/2849/consoleFull

2018-03-17 12:27:41 Unapproved licenses:
2018-03-17 12:27:41
2018-03-17 12:27:41 trafodion/Makefile
2018-03-17 12:27:41 trafodion/doap.rdf
2018-03-17 12:27:41 trafodion/env.sh
2018-03-17 12:27:41 trafodion/pom.xml
2018-03-17 12:27:41 trafodion/core/sql/common/11_ut2l.h
2018-03-17 12:27:41 trafodion/core/sql/common/1n_lt2u.h
2018-03-17 12:27:41 trafodion/core/sql/eh/00-readme
2018-03-17 12:27:41 trafodion/core/sql/export/AbortCallBack.h
2018-03-17 12:27:41 trafodion/docs/lob_guide/src/asciidoc/_chapters/about.adoc
2018-03-17 12:27:41 trafodion/docs/messages_guide/src/asciidoc/_chapters/about.adoc
2018-03-17 12:27:41 trafodion/docs/odb_user/src/asciidoc/_chapters/a_warnings.adoc

RAT apparently does not like https in the license statements.

Hmm.

Is that something we can fix in our RAT configurations?

I thought maybe it would be addressed in a later version of RAT than what we use, but I see no indication of that in their docs.
Maybe we have to stick with exact license text, even for the old http URL.

New Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/2494/

Test Failed. https://jenkins.esgyn.com/job/Check-PR-master/2494/

jenkins, retest

Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/2548/

Test Failed. https://jenkins.esgyn.com/job/Check-PR-master/2548/

Just checking up on this pull request to see if we can move it along. It looks like the only issue remaining is to change "https" back to "http" in the Apache license headers. @svarnau and @PierreSmits, do you agree?

It seems to me that having either https or http in the licence header should not invalidate the test.

We are just going by what RAT reports. There has been some discussion of this on the legel-discuss mail list, and it was suggested that even changing http to https in the license text is a change that would need to be dicussed and approved by the ASF.